Skip to content

K8s: make OLM distinction in limitation - #3975

Merged
kaitlynmichael merged 3 commits into
mainfrom
DOC-7054
Sep 15, 2026
Merged

kaitlynmichael merged 3 commits into
mainfrom
DOC-7054

Conversation

@kaitlynmichael

@kaitlynmichael kaitlynmichael commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Note

Low Risk
Documentation-only edits to release notes with no product or deployment logic changes.

Overview
Updates the Known limitations note on the 7.22.2-43 and 8.0.20-26 August 2026 release pages so the blocked upgrade path applies specifically to OLM-based deployments, not all install methods.

The guidance no longer tells customers to stay on 7.22.2-43 until a newer 8.0.20 build; it now directs them to upgrade to 8.0.20-27 or later instead of stopping at 8.0.20-26.

Reviewed by Cursor Bugbot for commit d6f17e4. Bugbot is set up for automated code reviews on this repo. Configure here.

@kaitlynmichael
kaitlynmichael requested a review from a team September 10, 2026 17:32
@kaitlynmichael kaitlynmichael self-assigned this Sep 10, 2026
@github-actions

github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

DOC-7054

@github-actions

github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 10 related items from repository history (5 new this commit):

Memory updated at d6f17e4

@joecreanrl

joecreanrl commented Sep 10, 2026

Copy link
Copy Markdown

hey @Kaitlyn Michael i personally would like to see this comment from the DOC ticket in there too

(Operator Lifecycle Manager / ClusterServiceVersion, i.e. OperatorHub-managed operator upgrades)

make it clear that its OperatorHub .. that means that the Operator is not upgradable from OperatorHub which is what people need to know.

Is a workaround to not use OperatorHub and the CLI instead? Admiittedly most Openshift customers will want to use OperatorHub.

Also just for clarification it is only 7.22.2-43 and not any 7.22.2 version before or after it right?

@mich-elle-luna mich-elle-luna left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you!

@kaitlynmichael

Copy link
Copy Markdown
Contributor Author

Kept "OLM-based deployments" rather than naming OperatorHub — engineering confirmed this affects all OLM-managed upgrades, not just the ones started from OperatorHub. That also rules out the CLI as a workaround: a Subscription applied from the CLI hits the same upgrade graph, so only a non-OLM install (Helm or manifests) avoids it. And yes, it is specific to the 7.22.2-43 to 8.0.20-26 combination.

I also replaced the second sentence since you looked. It said to remain on 7.22.2-43 until a later 8.0.20 release was available; 8.0.20-27 shipped on September 9 with the fix, so both pages now point there.

@kaitlynmichael
kaitlynmichael merged commit 57c2c73 into main Sep 15, 2026
99 checks passed
@kaitlynmichael
kaitlynmichael deleted the DOC-7054 branch September 15, 2026 15:15
EliShteinman added a commit to EliShteinman/docs that referenced this pull request Sep 15, 2026
Narrows the 7.22.2-43 to 8.0.20-26 Kubernetes upgrade limitation to OLM-based deployments and points readers to 8.0.20-27 or later instead of staying on 7.22.2-43.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Bd1E1uKP1YNiY24wiw2U7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants